Conferencing PSTN gateway methods and apparatus to facilitate heterogeneous wireless network handovers for mobile communication devices

ABSTRACT

Techniques for use in a network processing component is for initially establishing, via a gateway, a voice call between a mobile device which operates in a wireless network and a destination device. A first connection leg of the voice call is to be established between the mobile device and a conference room of the gateway. The technique involves sending to the gateway a request message for establishing a second connection leg between the network processing component and the destination device, and then subsequently sending to the gateway a re-routing message for re-routing the second connection leg from the network processing component to the conference room. This causes a voice call having the first and the second connection legs to be initially established between the mobile device and the destination device via the gateway.

CROSS-REFERENCE TO RELATED APPLICATIONS

This patent application is a continuation of and claims priority tonon-provisional patent application having application Ser. No.11/534,371 and filing date of 22 Sep. 2006, now U.S. Pat. No. 7,986,665,which claims priority to U.S. provisional patent application havingapplication No. 60/719,803 and filing date of 23 Sep. 2005, eachapplication being hereby incorporated by reference herein.

BACKGROUND

1. Field of the Technology

The present disclosure relates generally to methods and apparatus forestablishing and handling voice calls for mobile communication devicesto facilitate handovers of the voice calls between heterogeneouswireless networks (e.g. WLAN/802.11/SIP technologies vs. WWAN/cellulartechnologies).

2. Description of the Related Art

The present disclosure is generally directed to techniques forestablishing and handling voice calls for mobile communication devicesin order to facilitate handovers of the voice calls betweenheterogeneous wireless communication networks. A particular focus isdirected to voice calls between mobile communication devices andcommunication devices in the public switched telephone network (PSTN),and inter-enterprise voice calls between communication devices in thesame communication network.

A mobile communication device may be adapted for wireless communicationsvia a wireless local area network (WLAN), such as an WLAN utilizing IEEE802.11 and Voice over IP (VoIP) based communications, as well as awireless wide area network (WWAN), such as a cellular telecommunicationsnetwork utilizing Global Systems for Mobile Communications (GSM)/GeneralPacket Radio Service (GPRS) technologies, for example. VoIP is enabledin part by use of a Session Initiation Protocol (SIP). AlthoughSIP-enabled networks carrying VoIP communications are quickly growing asa percentage of the communications market, they still represent a smallpercentage of the overall voice market. Therefore, such SIP-enablednetworks must be able to communicate with other types of networks,especially via the PSTN.

When a voice call involving the mobile communication device and a PSTNdestination is established, it is desirable to seamlessly maintain thevoice call even though the mobile communication device may switchoperation between the WLAN and WWAN. To accomplish this, the voice callmay be routed through a conferencing gateway to facilitate the handoverof the voice call between the WLAN and WWAN. For voice calls betweencommunication devices of the same private communication network (e.g.the same private LAN of an enterprise such as a company or corporation),however, use of the conferencing gateway may not be necessary in caseswhere no handover will ever occur. As apparent, use of the conferencinggateway for all such voice calls creates an unnecessary and undue burdenon the conferencing gateway and perhaps unnecessary expense.

Accordingly, there are needs for methods and apparatus to establish andhandle voice calls for mobile communication devices to facilitatehandovers of voice calls between heterogeneous wireless networks,especially between communication devices of the same communicationnetwork, so as to overcome the deficiencies of the prior art.

BRIEF DESCRIPTION OF THE DRAWINGS

Embodiments of present invention will now be described by way of examplewith reference to attached figures, wherein:

FIG. 1 is an illustrative representation of a communication system whichincludes a wireless local area network (WLAN) (such as an 802.11-basedwireless network) of a LAN and a wireless wide area network (WWAN) (suchas a cellular telecommunications network) of a WAN;

FIG. 2 is a schematic diagram of a mobile communication device which mayoperate in both the WLAN and the WWAN of FIG. 1;

FIG. 3 is an illustrative depiction of functional modules and layers ofthe mobile communication device of FIG. 2;

FIG. 4 shows pertinent components of the communication system of FIG. 1which illustrates the basic approach of the present disclosure utilizinga conferencing PSTN conferencing gateway;

FIG. 5A is a process flow diagram which describes a method for use inestablishing and handling a voice call involving the mobile device and acommunication device in the LAN, and subsequently transferring the voicecall through the conferencing gateway;

FIG. 5B is a process flow diagram which describes a variation on themethod of FIG. 5A;

FIG. 5C is a process flow diagram which describes another variation onthe methods of FIGS. 5A-5B;

FIG. 6 is a process flow diagram for describing a conferencing PSTNmethod for use in establishing and handling a voice call involving themobile device initially operating in the WLAN and a PSTN communicationdevice, and for handing off such voice call from the WLAN to the WWANfor the mobile device; and

FIG. 7 is a process flow diagram for describing a conferencing PSTNmethod for use in establishing and handling a voice call involving themobile device initially operating in the WWAN and the PSTN communicationdevice, and for handing off such voice call from the WWAN to the WLANfor the mobile device.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

In one illustrative embodiment of the present disclosure, a mobilecommunication device operating in a wireless local area network (WLAN)of a communication network maintains an inter-enterprise voice call viaits WLAN interface with another communication device in thecommunication network. Communications of the voice call are maintainedsolely within the communication network and not routed through aconferencing gateway. During the voice call, a handover of the voicecall from the WLAN to a wireless wide area network (WWAN) may or may notbe required. In response to identifying a handover indication during thevoice call, the mobile device causes a request message to be sent overthe WWAN to the conferencing gateway for establishing a first connectionleg over the WWAN via its WWAN interface with a conference room of theconferencing gateway. The mobile device also causes a re-routing messageto be sent over the WLAN to the communication device, so that a secondconnection leg between the communication device and the conference roomof the conferencing gateway may be established. The first and the secondconnection legs are connected together in the conference room of theconferencing gateway for the voice call. Advantageously,inter-enterprise voice calls need not unnecessarily and unduly burdenthe conferencing gateway, unless and until a handover of the voice callbetween the WLAN and the WWAN is required. Variations and other PSTNconferencing gateway techniques are also described.

In a technique for a voice call with a PSTN destination, a conferencingPSTN gateway is utilized and treated as a centralized entity. A voicecall through a WLAN interface of a mobile device to a PSTN communicationdevice includes two connection legs to the conferencing gateway, namely,a connection leg 1 from the WLAN interface of the mobile device to theconferencing gateway, and a connection leg 2 from the conferencinggateway to the PSTN communication device. When performing a handoff,connection leg 1 is substituted with a newly-established connection leg3 from a WWAN interface of the mobile device to the conferencinggateway, rather than directly to PSTN communication device itself. Theconferencing gateway utilizes conferencing techniques, which includetranscoding and mixing the media streams, for all connection legs. Thisapproach allows for a true soft, seamless handoff, where the sessionfrom the PSTN communication device to the conferencing gateway is notaffected by the handoff, and where there is a controllable overlapbetween the two media streams flowing from the two interfaces of themobile device to the conferencing gateway.

In such technique, in response to identifying a voice call request forthe voice call, a first connection leg for the voice call is establishedbetween the mobile device in the wireless network and a conference roomof the conferencing gateway. In addition, a second connection leg isestablished between a call coordinating processor and the communicationdevice through the PSTN. Subsequently, the second connection leg istransferred from the call coordinating processor to the conference roomof the conferencing gateway, so that the second connection leg for thevoice call is established between the conference room of theconferencing gateway and the communication device. Voice communicationsfor the voice call may then be maintained through the first and thesecond connection legs via the conferencing gateway. For any subsequenthandover of the voice call between heterogeneous wireless networks (e.g.WLAN to WWAN, or WWAN to WLAN), a third connecting leg for the voicecall may be established between the mobile device and the conferenceroom of the conferencing gateway, and the first connecting leg may beterminated.

Introducing the basic system architecture, FIG. 1 is an illustration ofa communication system 100 which may embody the methods and apparatus ofthe present disclosure. Communication system 100 includes a wirelesswide area network (WWAN) 102, a local area network (LAN) 104 whichincludes a wireless LAN (WLAN) 106, and a mobile communication device108 which is operative to wirelessly communicate in both WWAN 102 andWLAN 106. Also shown in FIG. 1 is a public switched telephone network(PSTN) 105 communicatively coupled to WWAN 102 and LAN 104, and a publiccommunication network 125 (e.g. the Internet) coupled to LAN 104. PSTN105 may be referred to more generally as a public telephone network.

At least some communication devices (e.g. terminals, computer devices)in LAN 104 are mobile/wireless/RF devices (e.g. mobile device 108) whichinterface and communicate via one or more wireless access points (APs)112 of WLAN 106. Such mobile devices 108 and wireless APs 112 mayoperate and communicate in accordance with well-known IEEE 802.11standards specifications. For example, mobile device 108 includes a WLANinterface 122 for communications via WLAN 106. For communications viaWLAN 106, mobile device 108 needs to be located within a coverage regionof WLAN 106.

LAN 104 provides various data and communication services tocommunication devices with access to it, whether through directionconnection or via WLAN 106. LAN 104 may provide for voice telephonycommunication services, for example, with use of Voice over IP (VoIP)technologies. For VoIP communication sessions, LAN 104 may utilize aVoIP server architecture which includes at least one VoIP or SessionInitiation Protocol (SIP) proxy registrar or server 152. SIP iswell-documented in standard specification documents such as Request ForComments (RFC) 3261. In addition, a Real-time Transport Protocol (RTP)or other suitable protocol may be used for the transport of data packetsof the media stream during such calls. Thus, communication applicationsof the devices provide for communications in accordance with the SIP andrelated protocols. Communication devices in LAN 104 are therebyoperative to establish and maintain voice calls with other communicationdevices connected in LAN 104, with other communication devices in publicnetwork 125 (e.g. a communication device 118), and with othercommunication devices in PSTN 105 (e.g. a communication device 116)using a conferencing gateway 150 which is described later herein. Notethat the wireless APs of WLAN 106 and related entities do notnecessarily have to be in the same LAN 104 for proper operation, butthey must be able to route data packets amongst themselves (e.g. amobile device that is associated with a wireless AP must be able toregister with SIP server 152 regardless of whether it is located in thesame LAN 104 or if is located in public network 118).

A router or NAT router 154 is provided in LAN 104 to facilitate IP datapacket communications for communication devices. NAT router 154, whichmay utilize Network Address Translation (NAT) techniques, allows LAN 104to use one set of IP addresses for internal IP traffic and a second setof IP addresses for external IP traffic. NAT router 154 also serves as atype of firewall by hiding internal IP addresses of LAN 104 from theoutside. Finally, NAT router 154 is operative to combine multipleconnections associated with different communication devices into asingle Internet connection. As illustrated in FIG. 1, NAT router 154 hascommunication interfaces for being communicatively coupled to publicnetwork 125 (e.g. the Internet), the wireless APs of WLAN 106 (e.g.connecting with wireless AP 112), LAN network servers such as SIP proxyserver 152, and conferencing gateway 150. In the present embodiment, LAN102 is a private communication network which includes a firewall toprevent unauthorized communication access to LAN 102 from outside of LAN102, such as via public network 125.

WWAN 102 is preferably a cellular telecommunications network. In thepresent embodiment, WWAN 104 conforms to Global System for MobileCommunications (GSM) and General Packet Radio Service (GPRS)communication technologies. Thus, WWAN 102 is built upon a well-knownGSM/GPRS architecture which includes a Public Land Mobile Network (PLMN)110 and a plurality of base stations 155 (such as a base station 140)communicatively coupled to PLMN 110, and a Gateway Mobile SwitchingCenter (GMSC) 114 communicatively coupled between PLMN 110 and PSTN 105.PLMN 110 may be more generally referred to as a core WAN of WWAN 104,and GMSC 114 may be more generally referred to as a communicationgateway. As indicated in FIG. 1, mobile device 108 includes a WWANinterface 120 for communications via WWAN 102, in addition to its WLANinterface 122 for communications via WLAN 106. For communications viaWWAN 102, mobile device 108 needs to be located within a coverage regionof WWAN 102.

PSTN conferencing gateway 150 (“conferencing gateway 150”) is also shownin FIG. 1. As will be described herein, conferencing gateway 150 isoperative to facilitate the establishment of voice calls betweencommunication devices having different communication protocols andinterfaces, as well as to facilitate the handover of such voice callsbetween heterogeneous wireless networks (e.g. WWAN 102 and WLAN 106) formobile communication devices. Such operation is achieved through use ofseparate call connection legs for voice calls and conference roomconnections. In one embodiment, conferencing gateway 150 is an IP-PBX ofthe communication network.

As illustrated in FIG. 1, conferencing gateway 150 utilizes at leastthree communication interfaces 160, 162, and 164 for such operation.These three interfaces may be separate physical interfaces, or separatefunctional or logical interfaces. Communication interface 160 ofconferencing gateway 150 is a PSTN or foreign exchange office (FXO)interface which provides conferencing gateway 150 with a communicativecoupling to PSTN 105 (and thus to WWAN 102 and mobile device 108 via itsWWAN interface 120). Communication interface 162 of conferencing gateway150 is another PSTN or FXO interface which provides conferencing gateway150 with another communicative coupling to PSTN 105 to provideconferencing gateway 150 with another communicative coupling to PSTN 105(and thus to a PSTN destination such as communication device 116).Finally, communication interface 164 of conferencing gateway 150 is anEthernet communication interface which provides conferencing gateway 150with a communicative coupling to NAT router 154 (and thus tocommunication devices in LAN 104 including mobile device 108 via itsWLAN interface 122).

A gateway typically has N interfaces, where N is the number of differenttype networks that the gateway is interconnecting. To allow for basicinterworking between different types of networks, conferencing gateway150 is adapted to perform two tasks: (1) signal conversion by asignaling module; and (2) media stream conversion by a media gatewaymodule. ISDN User Part (ISUP) signaling is converted into SIP signalingby the signaling module, and vice versa. With the media gateway module,the voice steam arriving at PSTN 150 is converted into Real-timeTransport Protocol (RTP) media stream at the ingress point of LAN 104,and likewise it is converted into a PSTN media stream at the ingresspoint of PSTN 150. Even though the signaling module and the mediagateway module may be considered as two separate logical entities, thereis nothing preventing them from residing at the same physical entity inconferencing gateway 150. A media gateway control module may be utilizedto implement a control protocol, such as a Media Gateway ControlProtocol (MGCP), to perform handshaking between the signaling module andthe media gateway module.

Conferencing gateway 150 generally serves as a media stream mixer.Centralized conference rooms may be created, where multiple mediastreams may be mixed together. Some telephony devices with the abilityto establish two independent calls can perform the mixing locallywithout resorting to centralized conference rooms. Provisioningconference rooms at the gateway has some disadvantages, however. Forone, the mixing and conversion of the media stream (sometimes referredto as “transcoding”) is typically performed at one entity, which causesa computational pardon and possible degradation in voice quality.Secondly, conferencing consumes gateway interface availability (i.e.bandwidth in the case of VoIP, and channels in the case of PSTN). Thelatter disadvantage is unavoidable in the case of two heterogeneousdestinations, since they have to be routed through the gateway anywaybecause they require signal and media stream conversion. However,conferencing homogeneous destinations will expend the available channelsor bandwidth, which could be easily avoided by using terminal devicescapable of doing the mixing.

Referring now to FIG. 2, electrical components and operation of atypical mobile communication device 108 (e.g. a dual mode (DM) handset,)adapted to communicate via both WLANs and WWANs are now described.Mobile device 108 may be representative of one or more communicationdevices which operate in communication system 100 of FIG. 1. Preferably,mobile device 108 is a wireless handset which operates in accordancewith IEEE 802.11 standards and a cellular network interface standard(e.g. GSM/GPRS standards). Also preferably, mobile device 108 is atwo-way communication device having at least voice and advanced datacommunication capabilities, including the capability to communicate withother computer systems. Depending on the functionality provided bymobile device 108, it may be referred to as a data messaging device, atwo-way pager, a cellular telephone with data messaging capabilities, awireless Internet appliance, or a data communication device (with orwithout telephony capabilities).

As previously described, mobile device 108 is adapted to wirelesslycommunicate with wireless AP 112 of the WLAN. For communication withwireless AP 112, mobile device 108 utilizes WWAN interface 122. Mobiledevice 108 is also adapted to wirelessly communicate with base stations155 of the WWAN. With such configuration, mobile device 108 may bereferred to as a “dual mode” (DM) mobile device. Although mobile device108 may have (and/or be shown to have) separate and independentsubsystems for these purposes, at least some portions or components ofthese otherwise different subsystems may be shared where possible.

WWAN interface 122 includes a receiver 212, a transmitter 214, andassociated components, such as one or more (preferably embedded orinternal) antenna elements 216 and 218, local oscillators (LOs) 213, anda digital signal processor (DSP) 220. As will be apparent to thoseskilled in the field of communications, the particular design of WWANinterface 122 depends on the communication network in which mobiledevice 108 is intended to operate. In the present application, WWANinterface 122 (including its associated processor/processing components)are operative in accordance with GSM/GPRS specification standards.

Mobile device 108 may send and receive communication signals through thenetwork after required network procedures have been completed. Signalsreceived by antenna 216 through the network are input to receiver 212,which may perform such common receiver functions as signalamplification, frequency down conversion, filtering, channel selection,and like, and in example shown in FIG. 2, analog-to-digital (A/D)conversion. A/D conversion of a received signal allows more complexcommunication functions such as demodulation and decoding to beperformed in DSP 220. In a similar manner, signals to be transmitted areprocessed, including modulation and encoding, for example, by DSP 220.These processed signals are input to transmitter 214 fordigital-to-analog (D/A) conversion, frequency up conversion, filtering,amplification and transmission through the network via antenna 218. DSP220 not only processes communication signals, but may also provide forreceiver and transmitter control. Note that receiver 212 and transmitter214 may share one or more antennas through an antenna switch (not shownin FIG. 2), instead of having two separate dedicated antennas 216 and218 as shown.

WLAN interface 120 of mobile device 108, which is utilized for wirelesscommunications via wireless AP 112 of the WLAN, is structurally similarto that shown and described for WWAN interface 122. However, a baseband(BB) and media access control (MAC) processing module replaces DSP 220.Such WLAN interface 120 is adapted to operate in accordance withwell-known IEEE 802.11 standards.

As mobile device 108 may be a portable battery-powered device, it alsoincludes a battery interface 254 for receiving one or more rechargeablebatteries 256. Such a battery 256 provides electrical power to most ifnot all electrical circuitry in mobile device 202, and battery interface254 provides for a mechanical and electrical connection for it. Batteryinterface 254 is coupled to a regulator (not shown in FIG. 2) thatprovides a regulated voltage V to all of the circuitry.

Mobile device 108 includes a microprocessor 238 (one type of processoror controller) that controls overall operation of mobile device 202.This control includes the call establishment and handover techniques ofthe present application. Communication functions, including at leastdata and voice communications, are performed through radio interfaces120 and/or 122. Microprocessor 238 also interacts with additional devicesubsystems such as a display 222, a flash memory 224, a random accessmemory (RAM) 226, auxiliary input/output (I/O) subsystems 228, a serialport 230, a keyboard 232, a speaker 234, a microphone 236, a short-rangecommunications subsystem 240, and any other device subsystems generallydesignated at 242. Some of the subsystems shown in FIG. 2 performcommunication-related functions, whereas other subsystems may provide“resident” or on-device functions. Notably, some subsystems, such askeyboard 232 and display 222, for example, may be used for bothcommunication-related functions, such as entering a text message fortransmission over a communication network, and device-resident functionssuch as a calculator or task list. Operating system software used bymicroprocessor 238 is preferably stored in a persistent store such asflash memory 224, which may alternatively be a read-only memory (ROM) orsimilar storage element (not shown). Those skilled in the art willappreciate that the operating system, specific device applications, orparts thereof, may be temporarily loaded into a volatile store such asRAM 226.

Microprocessor 238, in addition to its operating system functions,preferably enables execution of software applications on mobile device108. A predetermined set of applications that control basic deviceoperations, including at least data and voice communicationapplications, will normally be installed on mobile device 108 during itsmanufacture. A preferred application that may be loaded onto mobiledevice 202 may be a personal information manager (PIM) applicationhaving the ability to organize and manage data items relating to usersuch as, but not limited to, e-mail, calendar events, voice mails,appointments, and task items. Naturally, one or more memory stores 224or 262 (where memory store 262 is a SIM which requires an interface 264)are available on mobile device 108 facilitate storage of PIM data itemsand other information.

The PIM application preferably has the ability to send and receive dataitems via the wireless network. Such PIM data items may be seamlesslyintegrated, synchronized, and updated via the wireless network, with thewireless device user's corresponding data items stored and/or associatedwith a host computer system thereby creating a mirrored host computer onmobile device 108 with respect to such items. This is especiallyadvantageous where the host computer system is the wireless deviceuser's office computer system. Additional applications may also beloaded onto mobile device 108 through network, an auxiliary I/Osubsystem 228, serial port 230, short-range communications subsystem240, or any other suitable subsystem 242, and installed by a user in RAM226 or preferably a non-volatile store (not shown) for execution bymicroprocessor 238. Such flexibility in application installationincreases the functionality of mobile device 108 and may provideenhanced on-device functions, communication-related functions, or both.For example, secure communication applications may enable electroniccommerce functions and other such financial transactions to be performedusing mobile device 108.

In a data communication mode, a received signal such as a text message,an e-mail message, or web page download will be processed by WWANinterface 122 and input to microprocessor 238. Microprocessor 238 willpreferably further process the signal for output to display 222 oralternatively to auxiliary I/O device 228. A user of mobile device 108may also compose data items, such as e-mail messages, for example, usingkeyboard 232 in conjunction with display 222 and possibly auxiliary I/Odevice 228. Keyboard 232 is preferably a complete alphanumeric keyboardand/or telephone-type keypad. These composed items may be transmittedover a communication network through one of the radio interfaces.

For voice communications, the overall operation of mobile device 108 issubstantially similar, except that the received signals would be outputto speaker 234 and signals for transmission would be generated bymicrophone 236. Alternative voice or audio I/O subsystems, such as avoice message recording subsystem, may also be implemented on mobiledevice 108. Although voice or audio signal output is preferablyaccomplished primarily through speaker 234, display 222 may also be usedto provide an indication of the identity of a calling party, duration ofa voice call, or other voice call related information, as some examples.

Serial port 230 in FIG. 2 is normally implemented in a personal digitalassistant (PDA)-type communication device for which synchronization witha user's desktop computer is a desirable, albeit optional, component.Serial port 230 enables a user to set preferences through an externaldevice or software application and extends the capabilities of mobiledevice 108 by providing for information or software downloads to mobiledevice 108 other than through a wireless communication network. Thealternate download path may, for example, be used to load an encryptionkey onto mobile device 108 through a direct and thus reliable andtrusted connection to thereby provide secure device communication.Short-range communications subsystem 240 of FIG. 2 is an additionaloptional component that provides for communication between mobile device108 and different systems or devices, which need not necessarily besimilar devices. For example, subsystem 240 may include an infrareddevice and associated circuits and components, or a Bluetooth™communication module to provide for communication with similarly enabledsystems and devices. Bluetooth™ is a registered trademark of BluetoothSIG, Inc.

Although a specific mobile device 108 has just been described, anysuitable mobile communication device or terminal may be part of theinventive methods and apparatus which will be described in fuller detailbelow.

FIG. 3 is an illustrative depiction of functional modules and layers ofmobile communication device 102 of FIGS. 1-2. Mobile device 108 of FIG.3 has three logical internal modules including an access module 308, atriggering module 306, and a physical layer module which consists ofWWAN interface 120 and WLAN interface 122. WWAN interface 120 includesvarious functional layers which vary depending on the communicationsstandard and, in the present embodiment, these layers are defined byGSM/GPRS standards. In FIG. 3, WWAN interface 120 is shown to include atleast a GSM codec 312 and a GSM baseband module 314. WLAN interface 122includes a VoIP client running a standard SIP 322, RTP 324 over UDP/IP326, 328 stack with an IEEE 802.11b physical layer 330. Note that twointerfaces 120 and 122 do not communicate directly with each other,however they communicate through access module 308. The behavior ofaccess module 308 depends on a configuration policy that is set by theend user, the manufacturer, the service provider, or any combination ofthese entities. The main task of access module 308 is to act as aninterface multiplexer in making calls and forwarding the associatedmedia stream in a data buffer 310. After being triggered by triggermodule 306, access module 308 orchestrates the handshaking between thetwo interfaces 120 and 122 in the midst of a handoff process. Forexample, assuming that access module 308 is configured to use WLANinterface 122 wherever coverage of the WLAN is available, if the enduser is in a location where no WLAN coverage exists, then access module308 establishes new calls over WWAN interface 120. Assuming that anactual call has been established over WWAN interface 120 and that, whilemoving, a suitable wireless AP link is detected at WLAN interface 122 bytriggering module 306, then access module 308 will be triggered tore-route the existing call via WLAN interface 122 and terminate the callvia WWAN interface 120, in accordance with the configuration policy.Triggering module 306 is an independent process that runs as a passivedaemon detecting the status of interfaces 120 and 122. Based onconfiguration parameters which are tightly coupled to the configurationpolicy defined at access module 308, triggering module 306 issues atrigger request to access module 308 which requests it to perform ahandoff. The design of triggering module 306 affects the system'soverall performance as it has to issue trigger requests early enough toallow access module 308 to establish a call over another interface, butat the same time trigger module 306 should avoid early and ping-pongtriggering (i.e oscillating between the two interfaces 120 and 122 dueto lack of physical layer behavior predictability).

There are some multiple proposals addressing handoff techniques betweenIP-based packet-switched over WWAN interface and WLAN interface. Suchproposals, however, are fundamentally different from the problem athand, since the IP-based WWAN technology is incapable of supportingvoice telephony at the current levels of available bandwidth and sinceplain circuit-switched telephony over WWAN is the current standard forWWAN voice telephony. Furthermore, the proposals for handoff betweenIP-based packet-switched over WWAN interface and WLAN interface are notapplicable to the handoff between plain circuit-switched telephony WWANinterface and the WLAN interface, due to the fundamental differencesbetween circuit-switched and packet-switched WWAN technologies. In thepresent disclosure, a loosely-coupled system is provided to perform areal-time, mid-call, bidirectional, vertical handoff between the WWANcircuit switched and WLAN packet-switched interfaces of mobile device108. A “mid-call” handoff implies that the switch between the twointerfaces 120 and 122 may occur while a media session is active and themedia stream is flowing end-to-end. The ability to keep the same mediasession active even when changing the underlying physical layer is achallenging task, which is further amplified by real-time constraints ofthe flowing media streams. Another constraint is to satisfy the“seamlessness” for the handoff. The definition of seamless handoff is avery elastic one depending on the level of user intervention, costfunction associated with the handoff (such as the switching time,dropped packets, or more subjectively a mean opinion score (MOS)).According to the present disclosure, seamlessness for a handoff existswhen the handoff requires no end-user intervention and when anacceptable level of voice quality is maintained during and after thehandoff.

FIG. 4 shows pertinent components of the communication system 100 ofFIG. 1 which illustrates one basic approach of the present disclosureutilizing conferencing gateway 150. Again, conferencing gateway 150 maybe an IP-PBX of the communication network. In the present disclosure,conferencing gateway 150 is treated as a centralized entity as shown inFIG. 4. A voice call through the WLAN interface of mobile device 108 toPSTN communication device 116 includes two connection legs, namely, aconnection leg 1 from the WLAN interface of mobile device 108 toconferencing gateway 150, and a connection leg 2 from conferencinggateway 150 to PSTN communication device 116. When performing a handoff,connection leg 1 is substituted with a newly-established connection leg3 from the WWAN interface of mobile device 108 to the PSTN interface ofthe conferencing gateway 150, rather than directly to PSTN communicationdevice 116 itself. Conferencing gateway 150 utilizes traditionalconferencing techniques for these connection legs, which includetranscoding and mixing the media streams for all three legs. Thisapproach allows for a true soft, seamless handoff, where the sessionfrom PSTN communication device 116 to conferencing gateway 150 is notaffected by the handoff, and where there is a controllable overlapbetween the two media streams flowing from the two interfaces of mobiledevice 108 to conferencing gateway 150. As apparent, being able toperform this type of handoff requires conferencing gateway 150 toprovide two PSTN interfaces when dialing a single PSTN communicationdevice 116. The reason is that one of these PSTN interfaces is used toestablish a connection leg from gateway 116 to PSTN communication device116, and the other is reserved for and/or utilized in the case of thehandoff.

For voice calls between communication devices of the same privatecommunication network (e.g. the same private LAN of an enterprise suchas a company or corporation), use of conferencing gateway 150 may not benecessary in cases where no handover will ever occur. As apparent, useof conferencing gateway 150 for all such voice calls creates anunnecessary and undue burden on the conferencing gateway and perhapsunnecessary expense.

FIG. 5A is a process flow diagram 501 for describing methods for use inestablishing and handling a voice call (e.g. a VoIP call) involvingmobile device 108 operating in the WLAN (i.e. 802.11-based networkutilizing SIP) of a communication network and another communicationdevice 550 of the communication network. Process flow diagram 501 isalso for describing methods for use in handing off such voice calls fromthe WLAN to the WWAN (e.g. GSM/GPRS network) for mobile device 108.Inventive techniques of FIG. 5A are performed by mobile device 108and/or conferencing gateway 150. The inventive techniques may be furtherpart of a computer program product which includes a computer readablemedium and computer instructions stored in the computer readable mediumfor use in being executed by one or more processors of mobile device 108and/or conferencing gateway 150. Preferably, in one embodiment,communication device 550 is a VoIP/SIP-enabled communication devicewhich is a “legacy” device, therefore requiring no modifications toaccommodate the techniques of the present disclosure. Also preferably,in another embodiment, conferencing gateway 150 is also a “legacy”device, therefore requiring no modifications to accommodate thetechniques of the present disclosure.

In the scenario described in relation to FIG. 5A, mobile device 108 isinitially operating in the WLAN. An end user of mobile device 108attempts to place a voice call to communication device 550 which islocated the communication network which includes the WLAN. Thus, thevoice call involving mobile device 108 may be referred to as aninter-enterprise voice call. A voice call request for this voice call isdetected via a user interface of mobile device 108. The voice callrequest includes a selected telephone number corresponding tocommunication device 550. In response to detecting the voice callrequest, mobile device 108 causes a request message for establishing thevoice call with communication device 550 to be communicated (step 502 ofFIG. 5A). The request message is transmitted by mobile device 108 viaits WLAN interface 122.

In this embodiment, the request message is an INVITE message of theSession Initiation Protocol (SIP). The INVITE message has a sourceidentifier corresponding to mobile device 108 (e.g. alice@xyz.org) and adestination identifier corresponding to communication device 550 (e.g.bob@xyz.org). Communication device 550 receives this request messageand, in response, sends a response message (e.g. 200 OK message of theSIP) back to mobile device 108 (step 504 of FIG. 5A). Mobile device 108receives this response message through its WLAN interface 122 and, inresponse, sends an acknowledgement message (e.g. an ACK message of theSIP) back to communication device 550 (step 506 of FIG. 5A). From steps502, 504, and 506, there is now a connection and a real-time mediastream established between mobile device 108 (i.e. via its WLANinterface 122) and communication device 550 for the voice call (step 508of FIG. 5A). As apparent, the connection and media stream for the voicecall are maintained entirely within the communication network and arenot routed through conferencing gateway 150. A Real-time TransportProtocol (RTP) or other suitable protocol may be used for the transportof data packets of the media stream.

Sometime during the voice call, mobile device 108 operating in the WLANmay receive an indication to perform a WLAN-to-WWAN handover (step 580of FIG. 5A). This handover (HO) trigger indication may be received inresponse to one or more of a variety of different events in mobiledevice 108 and/or its associated communication network. For example, theevents may be or include the detection of a low receive signal strengthof RF signals at mobile device 108 from APs in the WLAN, the detectionof a request at mobile device 108 by an end user, as some examples. Inresponse to detecting this indication at step 580, mobile device 108performs steps to facilitate a handover of the voice call from the WLANto the WWAN. Mobile device 108 achieves this by causing two separateconnection legs to be established and routed into a conference room ofconferencing gateway 150, so that the voice call may continue throughconferencing gateway 150.

Initially, mobile device 108 helps cause a first connection leg for thevoice call to be established between its WWAN interface 120 andconferencing gateway 150 in the following steps 510, 512, and 514 to bedescribed. In particular, mobile device 108 causes a request message toestablish the first connection leg to be communicated (step 510 of FIG.5A). This request message is transmitted via WWAN interface 120 ofmobile device 108. In general, the request message causes a PSTN trunkconnection in the PSTN to be reserved. In this embodiment, the requestmessage is an Initial Address Message (IAM) of an ISDN User Part (ISUP)protocol. ISUP is a protocol used between telephone switches in the PSTNfor call signaling, and is used over a dedicated packet-switched networkwith SS7 for transport. An IAM is typically used by an SSP to reserve anidle trunk circuit from an originating switch (e.g. at mobile device108) to a destination switch (e.g. at the conference room ofconferencing gateway 150), and typically includes data such as anoriginating point code, a destination point code, a circuitidentification code, and “dialed digits” corresponding to thedestination (e.g. the conference room of conferencing gateway 150).

Here, conferencing gateway 150 proceeds to process the incoming “call”(i.e. the IAM) from mobile device 108, but the message is properlyidentified by conferencing gateway 150 as being from mobile device 108for the purpose of the handover. In particular, conferencing gateway 150causes a notification message (e.g. a NOTIFY message of the SIP) to besent to mobile device 108 for receipt via its WLAN interface 122 (step512 of FIG. 5A), in order to signal that the handover is proceeding.Conferencing gateway 150 also causes a response to the request messageto be sent back to mobile device 108 for receipt via its WWAN interface120 (step 514 of FIG. 5A). In this embodiment, the response message isan Address Complete Message (ACM) of the ISUP protocol, which indicatesthat the remote end of the trunk has indeed been reserved. Typically, aSignal Transfer Point (STP) in the PSTN routes an ACM to the originatingswitch (e.g. at mobile device 108) which causes its line to “ring” andconnects the line to the PSTN trunk to complete a voice circuit betweenthe call parties. Here, little or no perceptible activity (audible orotherwise) is present at mobile device 108 during this silent andautomatic handover process. Conferencing gateway 150 then causes ananswer message (e.g. an ANM of the ISUP protocol) to be sent to mobiledevice 108 for receipt via its WWAN interface 120 (also step 514 of FIG.5A). The STP routes the ANM to mobile device 108 to verify that the linkto the conference room of conferencing gateway 150 is connected to thereserved trunk. After completion of steps 510, 512, and 514, mobiledevice 108 will have the first connection leg to the conference room ofconferencing gateway 150 established via its WWAN interface 120 for thevoice call (step 515 of FIG. 5A).

Next, mobile device 108 sends a call transfer or re-routing message tocommunication device 550 for transferring or re-routing its endpoint inthe original connection (step 516 of FIG. 5A). In particular, thisre-routing message is used for re-routing the connection such that asecond connection leg of the voice call is established between theconference room of conferencing gateway 150 and communication device550. In the present embodiment, mobile device 108 sends a REFER messageof the SIP in step 516. This REFER message may have a destinationidentifier corresponding to communication device 550 (e.g. bob@xyz.org)and a REFER-TO header corresponding to the conference room ofconferencing gateway 150 (e.g. cnf rm@xyz.org).

In response to receiving the re-routing message of step 516,communication device 550 causes the connection with mobile device 108 tobe transferred or re-routed into the conference room of conferencinggateway 150 in the following steps 518, 520, 522, 524, and 526.Initially, communication device 550 causes a response message (e.g. a202 ACCEPTED message of the SIP) to be sent back to mobile device 108(step 518 of FIG. 5A). Communication device 550 then causes a requestmessage for the re-routing (i.e. for establishing the second connectionleg) to be sent to the conference room of conferencing gateway 150 (step520 of FIG. 5A). In this embodiment, the request message is an INVITEmessage of the SIP. The INVITE message has a source identifiercorresponding to communication device 550 (e.g. bob@xyz.org) and adestination identifier corresponding to the conference room ofconferencing gateway 150 (e.g. cnf rm@xyz.org). Conferencing gateway 150receives this request message and, in response, sends a response message(e.g. 200 OK message of the SIP) back to communication device 550 (step522 of FIG. 5A). Communication device 550 receives this response messageand, in response, sends an acknowledgement message (e.g. an ACK messageof the SIP) back to the conference room of conferencing gateway 150(step 524 of FIG. 5A). Communication device 550 then causes anotification message (e.g. a NOTIFY message of the SIP) to be sent tomobile device 108 for receipt via its WLAN interface 122 (step 526 ofFIG. 5A). Upon completion of steps 520, 522, and 524, the secondconnection leg of the voice call has been established betweencommunication device 550 and the conference room of conferencing gateway150.

At this point in time, the two connection legs have been established:the first connection leg between mobile device 108 and the conferenceroom of conferencing gateway 150, and the second connection leg betweenthe conference room of conferencing gateway 150 and communication device550. Since conferencing gateway 150 earlier identified the requestmessage in step 520 (or other messages or indications) to be fromcommunication device 550 for the purpose of the handover, conferencinggateway 150 causes the two connection legs in the conference room to beconnected in a conference call connection. Thus, the voice call betweenmobile device 108 (via its WWAN interface 120) and communication device550, including its associated media stream, is established throughconferencing gateway 150 (step 528 of FIG. 5A) withindependently-severable connection legs. Again, the RTP or othersuitable protocol may be used for the transport of data packets of themedia stream.

FIG. 5B is a process flow diagram 503 which describes a variation on themethod of FIG. 5A. Recall that the method described in relation to FIG.5A revealed that a connection leg between WWAN interface 120 of mobiledevice 108 and gateway 150 could be established first (or caused to beestablished first) and/or prior to establishing the connection legbetween communication device 550 and gateway 150. Such a technique ofFIG. 5A may be preferred since the connection leg between WWAN interface120 of mobile device 108 and gateway 150 may inherently take relativelylonger to establish than the other connection leg; therefore, the timeto complete the handover may be reduced by establishing this leg first.

The variation in FIG. 5B, however, reveals that the connection legbetween communication device 550 and gateway 150 could be establishedfirst (or caused to be established first) and/or prior to establishingthe connection leg between WWAN interface 120 of mobile device 108 andgateway 150. Steps 516, 518, 520, 522, 524, 526, and 528 (bracketed as agroup of steps 545 in FIG. 5B) for performing the call re-routing orcall transfer are performed first instead of last. Also, previous steps510, 512, and 514 (bracketed as a group of steps 555 in FIG. 5B) forestablishing the WWAN connection leg are performed last instead offirst. Finally, an intermediary connection leg 538 between WLANinterface 122 of mobile device 108 and communication device 550 viaconferencing gateway 150 may be established. In FIG. 5B, intermediaryconnection leg 538 is established prior to establishing the connectionleg between WWAN interface 120 of mobile device 108 and gateway 150. Theintermediary connection leg in step 538 is established by steps 532,534, and 536 (bracketed as a group of steps 540) with use of messagingpreviously described (e.g. INVITE, etc.). In an alternate embodiment,these grouped steps 540 are performed prior to grouped steps 545 so thatintermediary connection leg 538 is established prior to the mediasession of step 528. After the media session of step 528 is established,intermediary connection leg 538 is terminated by mobile device 108 bysending a termination message (a BYE message of the SIP) in step 592which is acknowledged (a 200 OK message of the SIP) in step 594.

FIG. 5C is a process flow diagram 505 which describes another variationon the methods of FIGS. 5A-5B. The steps in process flow diagram 505 aresimilar to that shown and described in relation to FIG. 5B, however, thesending of the request message in step 510 (e.g. the IAM) is performedmuch earlier at a time reference marker 595 (e.g. prior to or at or nearthe same time as sending the re-rerouting message in step 516); this isdone in order to initiate the establishment of the connection legbetween WWAN interface 120 of mobile device 108 and gateway 150 prior togrouped steps 540 and 545. Steps 512 and 514 in FIG. 5C (bracketed as agroup of steps 556 in FIG. 5C), which are provided in response to therequest message of step 510, may occur following grouped steps 540 and545 as shown, or may occur somewhere in between such grouped steps.Again, as in the embodiment of FIG. 5B, the intermediary connection leg538 of FIG. 5C is established prior to establishing the connection legbetween WWAN interface 120 of mobile device 108 and gateway 150. Thisintermediary connection leg in step 538 is established by grouped steps540 with use of messaging previously described (e.g. INVITE message instep 532, OK message in step 536, and ACK message in step 536). In analternate embodiment, these grouped steps 540 are performed prior togrouped steps 545 so that the intermediary connection leg 538 isestablished prior to the media session of step 528 being established.

The variation of FIG. 5C may be preferred since the connection legbetween WWAN interface 120 of mobile device 108 and gateway 150 mayinherently take relatively longer to establish than the other connectionleg; therefore, the time to complete the handover may be reduced byinitiating the establishment of the WWAN connection leg first. Asapparent, the variation of FIG. 5C reveals that the steps for setting upthe connection legs into the conference room of gateway 150 may beoverlapped or interleaved, with the primary objective of reducing theoverall time to perform the handover. In fact, the connectionestablishment steps in any of the techniques of FIGS. 5A, 5B, and 5C maybe overlapped or interleaved where desired or preferred. As apparent,although each variation on the techniques described in relation to FIGS.5A, 5B, and 5C may have its own advantage and be preferred for suchadvantage, the ordering of the steps of the method may be varied as oneskilled in the art will readily appreciate.

Thus, a mobile communication device operating in a WLAN of acommunication network maintains an inter-enterprise voice call via itsWLAN interface with another communication device in the communicationnetwork. Communications of the voice call are maintained solely withinthe communication network and not routed through a conferencing gateway.During the voice call, a handover of the voice call from the WLAN to aWWAN may or may not be required. In response to identifying a handoverindication during the voice call, the mobile device causes a requestmessage to be sent over the WWAN to the conferencing gateway forestablishing a first connection leg over the WWAN via its WWAN interfacewith a conference room of the conferencing gateway. The mobile devicealso causes a re-routing message to be sent over the WLAN to thecommunication device, so that a second connection leg between thecommunication device and the conference room of the conferencing gatewaymay be established. The first and the second connection legs areconnected together in the conference room of the conferencing gatewayfor the voice call. Advantageously, inter-enterprise voice calls betweencommunication devices of the same communication network may beestablished so that the communications are contained entirely within thenetwork and not routed through conferencing gateway 150, with furthertechniques that allow for heterogeneous wireless network handovers androuting through conferencing gateway 150 when needed.

FIG. 6 is a process flow diagram 600 for describing methods for use inestablishing a voice call (e.g. a VoIP call) between mobile device 108initially operating in the WLAN (i.e. 802.11-based network utilizingSIP) and PSTN communication device 116 via conferencing gateway 150.Process flow diagram 600 is also for describing methods for use inhanding off such voice call from the WLAN to the WWAN (e.g. GSM/GPRSnetwork) for mobile device 108. A hairpin device 650, which interactswith mobile device 108 and conferencing gateway 150, and coordinates thecall establishment and handoff, is utilized for such techniques. Hairpindevice 650 may also be referred to as a call coordinating processor.Preferably, conferencing gateway 150 and hairpin device 650 areimplemented within the same physical processing component or server.Inventive techniques of FIG. 6 may be performed by mobile device 108,hairpin device 650, conferencing gateway 150, and/or a networkprocessing component which includes functionality of both hairpin device650 and conferencing gateway 150 (i.e. where hairpin device 650 andconferencing gateway 150 are co-located or part of the same architectureor server). The inventive techniques may be further part of a computerprogram product which includes a computer readable medium and computerinstructions stored in the computer readable medium for use in beingexecuted by one or more processors of mobile device 108, hairpin device650, conferencing gateway 150, and/or the component which includesfunctionality of both hairpin device 650 and conferencing gateway 150.

One particular problem is first addressed regarding a technique formobile device 108 to dial out to PSTN destinations via its WWANinterface 120. When dialing out via WWAN interface 120, it is desiredthat a connection leg is made to conferencing gateway 150 rather than tocommunication device 116 directly. This connection leg requires mobiledevice 108 to dial out to a Direct Inward Dialing (DID) number of thePSTN interface of conferencing gateway 150 via WWAN interface 120,followed by the dialing of the DID of communication device 116 byconferencing gateway 150, and placing both connection legs through theconference room of conferencing gateway 150. To do this, it would appearthat it is not possible for conferencing gateway 150 to dial tocommunication device 116 without being informed of the DID ofcommunication device 116 by the end user. If the end user would have todial both DIDs, this would violate the seamlessness requirement, sincethe user would have to dial the DID of conferencing gateway 150 firstand subsequently dial the DID of communication device 116 as anextension. The following technique may be utilized to alleviate suchconcern. As is conventional, the end user selects the DID ofcommunication device 116 when placing a voice call via WWAN interface120, and mobile device 108 is adapted to send this number via ShortMessage Service (SMS) (or via another suitable messaging) toconferencing gateway 150. At the same time, mobile device 108 is adaptedto automatically dial the DID of the PSTN interface of conferencinggateway 150 every time an outgoing call is placed via WWAN interface 120(or at least during times when the destination is a PSTN destination).During its initial configuration, mobile device 108 may programmed orhardcoded with the DID of the PSTN interface of conferencing gateway150. Conferencing gateway 150 has a daemon adapted to detect the SMSmessage, and anticipates the incoming call to it from mobile device 108via WWAN interface 120. Upon receipt of the incoming call, and detectionof the match with it and the SMS message, conferencing gateway 150forwards the call to communication device 150 with use of the DIDcontained in the SMS message.

Now continuing with reference to FIG. 6, mobile device 108 is initiallyoperating in the WLAN. An end user of mobile device 108 attempts toplace a voice call with PSTN communication device 116, and therefore avoice call request for the voice call is detected via a user interfaceof mobile device 108. The voice call request includes a selectedtelephone number corresponding to PSTN communication device 116. Inresponse to detecting the voice call request, mobile device 108 causes arequest message for establishing the voice call with the PSTNcommunication device 116 to be communicated (step 602 of FIG. 6). Inthis embodiment, the request message is an INVITE message of the SIPwhich has a source identifier corresponding to mobile device 108, adestination identifier corresponding to conferencing gateway 150 (e.g.dest@gw.com), and call party information corresponding to PSTNcommunication device 116. The request message is transmitted by mobiledevice 108 via its WLAN interface 122.

Although the destination identifier of the request message correspondsto conferencing gateway 150, the message is intercepted by hairpindevice 650. Alternatively, conferencing gateway 150 initially receivesthe request message but thereafter forwards it to hairpin device 650upon receipt. In any event, in response to receiving this requestmessage, hairpin device 650 attempts to establish a connection betweenitself and PSTN communication device 116 via conferencing gateway 150.In particular, hairpin device 650 causes a request message to be sent toconferencing gateway 150 (step 604 of FIG. 6). This request message mayalso be an INVITE message of the SIP which has a destination identifiercorresponding to conferencing gateway 150 (e.g. dest@gw.com) and callparty information corresponding to PSTN communication device 116;however, the source identifier of the request message corresponds tohairpin device 650.

In response to receiving the request message in step 604, conferencinggateway 150 causes a request message to be sent via the PSTN forconnecting with PSTN communication device 116 (step 606 of FIG. 6). Therequest message causes a PSTN trunk connection in the PSTN to bereserved for PSTN communication device 116. In this embodiment, therequest message is an Initial Address Message (IAM) of the ISUPprotocol. An IAM is typically used by a Service Switching Point (SSP) toreserve an idle trunk circuit from an originating switch (e.g. atconferencing gateway 150) to a destination switch, and typicallyincludes data such as an originating point code, a destination pointcode, a circuit identification code, and “dialed digits” correspondingto the destination (e.g. PSTN communication device 116).

In response to receiving the request message in step 606, a responsemessage is sent back to conferencing gateway 150 via the PSTN (step 608of FIG. 6). In this embodiment, the response message is an AddressComplete Message (ACM) of the ISUP protocol which indicates that theremote end of the trunk has indeed been reserved. Here, a SignalTransfer Point (STP) in the PSTN routes the ACM to the originatingswitch (e.g. at conferencing gateway 150) which causes its line to“ring” and connects the line to the PSTN trunk to complete a voicecircuit between conferencing gateway 150 and PSTN communication device116. When PSTN communication device 116 subsequently answers theincoming voice call, the destination switch terminates the ringing toneand transmits an answer message to conferencing gateway 150 via its homeSTP (step 610 of FIG. 6). In this embodiment, the answer message is ananswer message (ANM) of the ISUP protocol. The STP routes the ANM toconferencing gateway 150 to verify that the link to PSTN communicationdevice 116 is connected to the reserved trunk.

Upon completion of steps 606, 608, and 610, conferencing gateway 150causes a response message to be sent back to hairpin device 650 (step612 of FIG. 6). This response message is used to confirm the receipt andhandling of the request message (i.e. the INVITE message) sent fromhairpin device 650 back in step 604. In this embodiment, the responsemessage is a 200 OK message of the SIP. Note that an acknowledgement byhairpin device 650 in response to this request message, for establishingor confirming the connection leg between hairpin device 650 and PSTNcommunication device 116, will not be communicated until later in step624 of FIG. 6.

Next, hairpin device 650 causes a first connection leg to be establishedbetween mobile device 108 and the conference room of conferencinggateway 150. There are a number of ways to achieve such a connectionleg. In the present embodiment, conferencing gateway 150 causes amessage to be sent to mobile device 108 to initiate the process (step614 of FIG. 6). In particular, conferencing gateway 150 causes a 302Moved Temporarily message of the SIP to be sent to mobile device 108,which includes contact information of the conference room ofconferencing gateway 150 (e.g. cnf rm@gw.com). A 302 Moved Temporarilymessage may be used for call redirection purposes and includes a UniformResource Indicator (URI) that is not permanent.

Mobile device 108 receives the message in step 614 through its WLANinterface 122 and, in response, sends an acknowledgement message (e.g.an ACK message of the SIP) to conferencing gateway 150 (step 616 of FIG.6). Using the contact information received in the message from step 614,mobile device 108 further causes a request message (e.g. an INVITEmessage of the SIP) to be transmitted via its WLAN interface 122 to theconference room of conferencing gateway 150 (e.g. cnf rm@gw.com) (step618 of FIG. 6). Conferencing gateway 150 receives this message and, inresponse, sends a response message (e.g. 200 OK message of the SIP) backto mobile device (step 620 of FIG. 6). Mobile device 108 receives thisresponse message through its WLAN interface 122 and, in response, sendsan acknowledgement message (e.g. an ACK message of the SIP) back toconferencing gateway 150 (step 622 of FIG. 6). From steps 614-622, afirst connection leg of the voice call is now established between mobiledevice 108 (i.e. via its WLAN interface 122) and the conference room ofconferencing gateway 150.

Next, hairpin device 650 causes an acknowledgement message (e.g. an ACKmessage of the SIP) to be sent to conferencing gateway 150 in responseto the 200 OK message received previously in step 612 (step 624 of FIG.6). Upon conferencing gateway 150 receiving this acknowledgementmessage, a second connection leg is established between hairpin device650 and PSTN communication device 116 via conferencing gateway 150responsive to the earlier request message (i.e. the INVITE message) ofstep 604. At this point in time, two separate connection legs have beenestablished: the first connection leg between mobile device 108 (via itsWLAN interface 122) and the conference room of conferencing gateway 150,and the second connection leg between hairpin device 650 and PSTNcommunication device 116 routed through conferencing gateway 150.

Hairpin device 650 then sends a call transfer or re-routing message toconferencing gateway 150 for call transferring or re-routing the secondconnection leg (step 626 of FIG. 6). In particular, this re-routingmessage is used to establish a re-routed second connection leg betweenthe conference room of conferencing gateway 150 and PSTN communicationdevice 116. In the present embodiment, hairpin device 650 sends a REFERmessage of the SIP in step 626. This REFER message may have adestination identifier corresponding to PSTN communication device 116and a REFER-TO header corresponding to the conference room ofconferencing gateway 150 (cnf rm@gw.com). In this embodiment, the REFERmessage is intercepted, interpreted, and acted up by conferencinggateway 150. Conferencing gateway 150 may intercept the REFER messagesince it is operative to monitor all messages between hairpin device 650and PSTN communication device 116 and identify messages only of the“REFER” type having its own identifier (cnf rm@gw.com) to execute there-routing function.

In response to receiving the re-routing message of step 626,conferencing gateway 150 causes the second connection leg with PSTNcommunication device 116 to be re-routed to the conference room ofconferencing gateway 150. Conferencing gateway 150 also causes aresponse message (e.g. an ACCEPT message of the SIP) to be sent back tohairpin device 650 (step 628 of FIG. 6). Both mobile device 108 and PSTNcommunication device 116 now have connection legs into the conferenceroom of conferencing gateway 150. Previously, conferencing gateway 150identified the messages associated with the two different connectionlegs for the purpose of the handover, which therefore causes it toconnect the real-time media stream between mobile device 108 and PSTNcommunication device 116 in a conference call connection for the voicecall (step 630 of FIG. 6). The RTP or other suitable protocol may beused for the transport of data packets of the media stream. Thus, thevoice call between mobile device 108 and PSTN communication device 116via conferencing gateway 150 is established with independently-severableconnection legs at conferencing gateway 150.

Sometime during the voice call, mobile device 108 operating in the WLANmay receive an indication to perform a WLAN-to-WWAN handover (step 631of FIG. 6). This handover (HO) trigger indication may be received inresponse to one or more of a variety of different events in mobiledevice 108 and/or its associated network. For example, the events may beor include the detection of low receive signal strength of RF signals atmobile device 108 from APs in the WLAN, the detection of a request atmobile device 108 by an end user, as some examples. In response todetecting this indication at step 631, mobile device 108 helps cause athird connection leg to be established between its WWAN interface 122 ofmobile device 108 and the conference room of conferencing gateway 150 inthe following steps 632, 634, 636, 638, 640, and 642.

More particularly, mobile device 108 causes a request message for thethird connection leg to be transmitted via its WWAN interface 120 (step632 of FIG. 6). In general, the request message causes a PSTN trunkconnection in the PSTN to be reserved for mobile device 108. In thisembodiment, the request message is an IAM of the ISUP. An IAM istypically used by an SSP to reserve an idle trunk circuit from anoriginating switch (e.g. at mobile device 108) to a destination switch,and typically includes data such as an originating point code, adestination point code, a circuit identification code, and “dialeddigits” corresponding to the destination (e.g. conferencing gateway150).

Here, conferencing gateway 150 proceeds to process the incoming “call”(i.e. the IAM) from mobile device 108, but the message is properlyidentified as being from mobile device 108 for the purpose of handover.More particularly, conferencing gateway 150 converts the IAM into anINVITE message (and/or produces an INVITE message corresponding to theIAM) directed to the conference room for processing. The conference roomresponds to the INVITE message from conferencing gateway 150 byproducing a 180 Ringing message and submitting it to conferencinggateway 150. Conferencing gateway 150, in turn, causes a responsemessage to be sent back to mobile device 108 via the WWAN interface 120(step 636 of FIG. 6). In this embodiment, the response message is an ACMwhich indicates that the remote end of the trunk has indeed beenreserved. Typically, an STP in the PSTN routes an ACM to the originatingswitch (e.g. at mobile device 108) which causes its line to “ring” andconnects the line to the PSTN trunk to complete a voice circuit betweenthe call parties. Here, little or no perceptible activity (audible orotherwise) is present at mobile device 108 during this silent andautomatic handover process. Note that a traffic channel between mobiledevice 108 and a base station of the WWAN is also established so thatthe third connection leg can be established. The conference room willthen issue a 200 OK message to conferencing gateway 150 as a finalresponse to the INVITE/IAM. In response, conferencing gateway 150 causesan answer message (e.g. an ANM of the ISUP protocol) to be sent tomobile device 108 via WWAN interface 120. The STP routes the ANM tomobile device 108 to verify that the link to the conference room ofconferencing gateway 150 is connected to the reserved trunk. In responseto steps 632, 634, 636, and 638, mobile device 108 will have the thirdconnection leg to the conference room of conferencing gateway 150established via its WWAN interface 120 for voice communications of thevoice call with PSTN communication device 116.

Upon completion of steps 632, 634, 636, and 638, mobile device 108causes a request message to be sent for terminating the first connectionleg established via its WLAN interface 122 (step 640 of FIG. 6). In thepresent embodiment, the request message is a BYE message of the SIP forterminating a voice call. In response to receiving the request messagefor terminating the first connection leg, conferencing gateway 150causes a response message to be sent to mobile device 108 (step 612 ofFIG. 6). This response message is used to confirm the receipt andhandling of the request (i.e. the BYE message) sent from mobile device108. In this embodiment, the response message is a 200 OK message of theSIP. Thus, the first connection leg and its associated communicationsbetween WLAN interface 122 of mobile device 108 and conferencing gateway150 are terminated.

The third connection leg between WWAN interface 120 of mobile device 108and the conference room of conferencing gateway 150, however, remainsestablished for the voice communications of the voice call with PSTNcommunication device 116. Previously, conferencing gateway 150identified the request message of step 632 from mobile device 108 (orother messages or indications) for the purpose of the handover; thisidentification causes it to connect the real-time media stream betweenmobile device 108 and PSTN communication device 116 in a conference callconnection for the voice call (step 644 of FIG. 6). Again, the RTP orother suitable protocol may be used for the transport of data packets ofthe media stream. Preferably, the first connection leg (i.e. WLAN or SIPbased) and the third connection leg (i.e. WWAN based) are simultaneouslymaintained over at least some time period by the conference room ofconferencing gateway 150 and/or mobile device 108 so that a seamlesshandover may occur (i.e. “make before break” approach).

FIG. 7 shows a process flow diagram 700 for describing methods for usein establishing a voice call (e.g. a VoIP call) between mobile device108 initially operating in the WWAN (e.g. GSM/GPRS network) and PSTNcommunication device 116 via conferencing gateway 150. Process flowdiagram 700 is also for describing methods for use in handing off suchvoice call from the WWAN to the WLAN (e.g. 802.11-based networkutilizing SIP) for mobile device 108. Hairpin device 650, whichinteracts with mobile device 108 and conferencing gateway 150, andcoordinates call establishment and handoff, is utilized for suchtechniques. Hairpin device 650 may also be referred to as a callcoordinating processor. As described earlier above, conferencing gateway150 and hairpin device 650 are preferably implemented within the samephysical processing component or server (i.e. where hairpin device 650and conferencing gateway 150 are co-located or part of the samearchitecture or server). Inventive techniques described in relation toFIG. 7 may be performed by mobile device 108, hairpin device 650,conferencing gateway 150, and/or a component which includesfunctionality of both hairpin device 650 and conferencing gateway 150.The inventive techniques described in relation to FIG. 7 may be furtherpart of a computer program product which includes a computer readablemedium and computer instructions stored in the computer readable mediumfor use in being executed by one or more processors of mobile device108, hairpin device 650, conferencing gateway 150, and/or the networkprocessing component which includes functionality of both hairpin device650 and conferencing gateway 150.

In the scenario described in relation to FIG. 7, mobile device 108 isinitially operating in the WWAN. An end user of mobile device 108attempts to place a voice call with PSTN communication device 116, andtherefore a voice call request for the voice call is detected via theuser interface of mobile device 108. The voice call request includes aselected telephone number corresponding to PSTN communication device116. In response to detecting the voice call request, mobile device 108causes a request message for establishing the voice call with the PSTNcommunication device 116 to be communicated via its WWAN interface 120(step 702 of FIG. 7).

In this embodiment, the request message of step 702 is an IAM of theISUP protocol. An IAM is typically used by an SSP to reserve an idletrunk circuit from an originating switch (e.g. at mobile device 108) toa destination switch, and typically includes data such as an originatingpoint code, a destination point code, a circuit identification code, and“dialed digits” corresponding to the destination (e.g. PSTNcommunication device 116). In this case, the IAM of step 702 has adestination corresponding to the conference room of conferencing gateway150 (dest@gw.com) and includes call party information corresponding toPSTN communication device 116. In particular, mobile device 108 may usethe IAM to cause a Direct Inward Dialing (DID) number or access numberof the conference room of conferencing gateway 150 to be dialed,followed by the number of PSTN communication device 116 which may be(automatically) dialed as an extension. Mobile device 108 may cause themessage to be constructed in this special manner in response toidentifying that the voice call request (e.g. the selected telephonenumber) through the user interface is intended for a PSTN communicationdevice; otherwise the message may be constructed in a conventionalmanner. In any case, it is preferred that the technique remaintransparent to the end user of mobile device 108.

Although the destination identifier of the request message correspondsto conferencing gateway 150, the message is intercepted by hairpindevice 650. Alternatively, conferencing gateway 150 initially receivesthe request message but thereafter forwards it to hairpin device 650upon receipt. In response to receiving the request message in step 702,hairpin device 650 causes a response message to be sent back to mobiledevice 108 via its WWAN interface 120 (step 704 of FIG. 7). In thisembodiment, the response message is an ACM which indicates that theremote end of the trunk has been reserved. Typically, an STP in the PSTNroutes an ACM to the originating switch (e.g. at mobile device 108)which causes its line to “ring” and connects the line to the PSTN trunkto complete a voice circuit between the call parties. Note that atraffic channel between WWAN interface 120 of mobile device 108 and abase station of the WWAN is also established so that the connection legcan be established. Conferencing gateway 150 also causes an answermessage (e.g. an ANM of the ISUP protocol) to be sent to mobile device108 via WWAN interface 120 (step 706 of FIG. 7). The STP routes the ANMto mobile device 108 to verify that the link to the conference room ofconferencing gateway 150 is connected to the reserved trunk. In responseto steps 702, 704, and 706, a first connection leg for the voice call isestablished between mobile device 108 (via its WWAN interface 120) andthe conference room of conferencing gateway 150.

Upon completion of steps 702, 704, and 706, hairpin device 650 attemptsto establish a second connection leg between itself and PSTNcommunication device 116 via conferencing gateway 150. In particular,hairpin device 650 causes a request message to be sent to conferencinggateway 150 (step 708 of FIG. 7). This request message may also be anINVITE message of the SIP which has a destination identifiercorresponding to conferencing gateway 150 (e.g. dest@gw.com) and callparty information corresponding to PSTN communication device 116;however, the source identifier of the request message corresponds tohairpin device 650. In response to receiving the request message in step708, conferencing gateway 150 causes a request message to be sent viathe PSTN for connecting with PSTN communication device 116 (step 710 ofFIG. 7). The request message causes a PSTN trunk connection in the PSTNto be reserved for PSTN communication device 116. In this embodiment,the request message is an IAM of the ISUP protocol. An IAM is typicallyused by an SSP to reserve an idle trunk circuit from an originatingswitch (e.g. at conferencing gateway 150) to a destination switch (e.g.at PSTN communication device 116), and typically includes data such asan originating point code, a destination point code, a circuitidentification code, and “dialed digits” corresponding to thedestination (e.g. PSTN communication device 116).

In response to receiving the request message in step 710, a responsemessage is sent back to conferencing gateway 150 via the PSTN (step 712of FIG. 7). In this embodiment, the response message is an ACM of theISUP protocol which indicates that the remote end of the trunk hasindeed been reserved. Here, an STP in the PSTN routes the ACM to theoriginating switch (e.g. at conferencing gateway 150) which causes itsline to “ring” and connects the line to the PSTN trunk to complete avoice circuit between conferencing gateway 150 and PSTN communicationdevice 116. When PSTN communication device 116 subsequently answers theincoming voice call, the destination switch terminates the ringing toneand transmits an answer message to conferencing gateway 150 via its homeSTP (step 714 of FIG. 7). In this embodiment, the answer message is anANM of the ISUP protocol. The STP routes the ANM to conferencing gateway150 to verify that the link to PSTN communication device 116 isconnected to the reserved trunk.

Upon completion of steps 708, 710, 712, and 714, conferencing gateway150 causes a response message to be sent back to hairpin device 650(step 716 of FIG. 7). This response message is used to confirm thereceipt and handling of the request message (i.e. the INVITE message)sent from hairpin device 650 back in step 708. In this embodiment, theresponse message is a 200 OK message of the SIP. Hairpin device 650receives this response message and, in response, sends anacknowledgement message (e.g. an ACK message of the SIP) back toconferencing gateway 150 (step 718 of FIG. 7). From steps 708-718, thesecond connection leg is now established between hairpin device 650 andPSTN communication device 116 through conferencing gateway 150. Notethat two separate connection legs are actually maintained at this pointin time: the first connection leg between mobile device 108 (via WWANinterface 120) and the conference room of conferencing gateway 150, andthe second connection leg between hairpin device 650 and PSTNcommunication device 116 routed via conferencing gateway 150.

Hairpin device 650 then sends a call transfer or re-routing message toconferencing gateway 150 for call transferring or re-routing itsendpoint in the second connection leg (step 720 of FIG. 7). Inparticular, this re-routing message is used to establish a re-routedsecond connection leg between the conference room of conferencinggateway 150 and PSTN communication device 116. In the presentembodiment, hairpin device 650 sends a REFER message of the SIP in step720. This REFER message may have a destination identifier correspondingto PSTN communication device 116 and a REFER-TO header corresponding tothe conference room of conferencing gateway 150 (cnf rm@gw.com). In thisembodiment, the REFER message is intercepted, interpreted, and acted upby conferencing gateway 150. Conferencing gateway 150 may intercept theREFER message since it is operative to monitor all messages betweenhairpin device 650 and PSTN communication device 116 and identifymessages only of the “REFER” type having its own identifier (cnfrm@gw.com) to execute the re-routing function.

In response to receiving the re-routing message of step 720,conferencing gateway 150 causes the second connection leg with PSTNcommunication device 116 to be re-routed to the conference room ofconferencing gateway 150. Conferencing gateway 150 also causes aresponse message (e.g. an ACCEPT message of the SIP) to be sent back tohairpin device 650 (step 722 of FIG. 7). Both mobile device 108 and PSTNcommunication device 116 now have connection legs into the conferenceroom of conferencing gateway 150. Previously, conferencing gateway 150identified the messages associated with the two different connectionlegs for the purpose of the handover; this identification causes it toconnect the real-time media stream between mobile device 108 and PSTNcommunication device 116 in a conference call connection for the voicecall (step 724 of FIG. 6). The RTP or other suitable protocol may beused for the transport of data packets of the media stream. Thus, thevoice call between mobile device 108 and PSTN communication device 116via conferencing gateway 150 is established with independently-severableconnection legs at conferencing gateway 150.

Sometime during the voice call, mobile device 108 operating in the WWANmay receive an indication to perform a WWAN-to-WLAN handover (step 725of FIG. 7). This handover (HO) trigger indication may be received inresponse to one or more of a variety of different events in mobiledevice 108 and/or its associated network. For example, the events may beor include the detection of adequate signals from one or more APs of theWLAN, the detection of low receive signal strength of RF signals atmobile device 108 from all base stations in the WWAN, the detection of arequest at mobile device 108 by an end user, as some examples.

In response to detecting this indication at step 725, mobile device 108helps cause a third connection leg to be established between its WLANinterface 120 and conferencing gateway 150 in the following steps 726,728, 730, 732, and 734. More particularly, mobile device 108 causes arequest message (e.g. an INVITE message of the SIP) for the thirdconnection leg to be transmitted via its WLAN interface 122 to theconference room of conferencing gateway 150 (step 726 of FIG. 7).Conferencing gateway 150 receives this message and, in response, sends aresponse message (e.g. 200 OK message of the SIP) back to mobile device(step 728 of FIG. 7). Mobile device 108 receives this response messagethrough its WLAN interface 122 and, in response, sends anacknowledgement message (e.g. an ACK message of the SIP) back toconferencing gateway 150 (step 730 of FIG. 7). From steps 726, 728, and730, the third connection leg for the voice call is established betweenmobile device 108 (i.e. via its WLAN interface 122) and the conferenceroom of conferencing gateway 150.

In response to receiving the 200 OK message in step 728, confirming thatthe new connection leg is established, mobile device 108 further causesa release message (e.g. REL message) to be sent via its WWAN interface120 (step 732 of FIG. 7). When a party (e.g. mobile device 108) to avoice call hangs up, a REL message is typically generated by the SSP ofthat party and includes the location of the voice line that was used forthe call. When the SSP of the other party (i.e. PSTN communicationdevice 116) receives such REL message, it disconnects the voice line andreturns its status to idle. The SSP of the other party (i.e. PSTNcommunication device 116) then sends a release complete message (RLCmessage) to the SSP of the party that hung up (step 734 of FIG. 7).Thus, the first connection leg and its associated communications betweenWWAN interface 120 of mobile device 108 and conferencing gateway 150 areterminated.

The third connection leg between WLAN interface 122 of mobile device 108and the conference room of conferencing gateway 150, however, remainsestablished for the voice communications of the voice call with PSTNcommunication device 116. Previously, conferencing gateway 150identified the request message of step 726 from mobile device 108 (orother messages or indications) for the purpose of the handover; thisidentification causes it to connect the real-time media stream betweenmobile device 108 and PSTN communication device 116 in a conference callconnection for the voice call (step 736 of FIG. 7). Again, the RTP orother suitable protocol may be used for the transport of data packets ofthe media stream. Preferably, the first connection leg (i.e. WWAN based)and the third connection leg (i.e. WLAN or SIP based) are simultaneouslymaintained over at least some time period by conferencing gateway 150and/or mobile device 108 so that a seamless handover may occur (i.e.“make before break” approach).

Thus, as described, a mobile communication device operating in awireless local area network (WLAN) of a communication network maintainsan inter-enterprise voice call via its WLAN interface with anothercommunication device in the communication network. Communications of thevoice call are maintained solely within the communication network andnot routed through a conferencing gateway. During the voice call, ahandover of the voice call from the WLAN to a wireless wide area network(WWAN) may or may not be required. In response to identifying a handoverindication during the voice call, the mobile device causes a requestmessage to be sent over the WWAN to the conferencing gateway forestablishing a first connection leg over the WWAN via its WWAN interfacewith a conference room of the conferencing gateway. The mobile devicealso causes a re-routing message to be sent over the WLAN to thecommunication device, so that a second connection leg between thecommunication device and the conference room of the conferencing gatewaymay be established. The first and the second connection legs areconnected together in the conference room of the conferencing gatewayfor the voice call. Advantageously, inter-enterprise voice calls neednot unnecessarily and unduly burden the conferencing gateway, unless anduntil a handover of the voice call between the WLAN and the WWAN isrequired.

In addition, a conferencing gateway for use in establishing andmaintaining a voice call between a communication device in a PublicSwitched Telephone Network (PSTN) and a mobile communication device hasbeen described. The conferencing gateway has first, second, and thirdcommunication interfaces, a media stream mixing module, and a controlmodule. The first communication interface is adapted for IPcommunications with a computer network which includes a wireless localarea network (WLAN). The second communication interface is adapted forcommunications with the PSTN and a wireless wide area network (WWAN) viathe PSTN. The third communication interface is also adapted forcommunications with the PSTN. The media stream mixing module is coupledto the first, the second, and the third communication interfaces. Thecontrol module is adapted to cause a first connection leg for the voicecall to be established with the mobile communication device via one ofthe first communication interface and the second communicationinterface, where the first communication interface is utilized when themobile communication device is operating in the WLAN and the secondcommunication interface is utilized when the mobile communication deviceis operating in the WWAN. The control module is further adapted to causea second connection leg for the voice call to be established with thecommunication device in the PSTN via the third communication interface.In response to a handover of the voice call, the control module isfurther adapted to cause a third connection leg to be established withthe mobile communication device via the other one of the firstcommunication interface and the second communication interface, wherethe first communication interface is utilized when the mobilecommunication device has switched to operation in the WLAN and thesecond communication interface is utilized when the mobile communicationdevice has switched to operation in the WWAN.

The above-described embodiments of the present application are intendedto be examples only. The embodiments of the present disclosure weredirected to the specific example where the WLAN was an 802.11-basednetwork and the WWAN was a cellular telecommunications network. However,the WLAN and WWAN may be networks different from those networks, as longas the WLAN type network covers a smaller region relative to the WWANtype network. Specifically, for example, one of the networks may be aBluetooth-based network, and the other network may be a cellular networkor an 802.11-based network. Also, for example, one of the networks maybe a WiMAX network, and the other network may be a cellular network oran 802.11-based network. Those of skill in the art may effectalterations, modifications and variations to the particular embodimentswithout departing from the scope of the application. The inventiondescribed herein in the recited claims intends to cover and embrace allsuitable changes in technology.

1. A method for use in a network processing component for initiallyestablishing, via a gateway, a voice call between a mobile device whichoperates in a wireless network and a destination device, wherein a firstconnection leg of the voice call is to be established between the mobiledevice and a conference room of the gateway, the method comprising:receiving, from the mobile device and at the network processingcomponent, a request message for establishing the voice call which isdirected to a selected telephone number of the destination device; inresponse to receiving the request message for establishing the voicecall: sending, from the network processing component to the gateway, arequest message for establishing a second connection leg between thenetwork processing component and the destination device; and sending,from the network processing component to the gateway, a re-routingmessage for re-routing the second connection leg from the networkprocessing component to the conference room, for initially establishingthe voice call between the mobile device and the destination device viathe gateway, the voice call including the first and the secondconnection legs.
 2. The method of claim 1, wherein the mobile deviceoperates in a wireless network comprising a first wireless network and,in response to a handover indication, a third connection leg isestablished between the mobile device which operates in a secondwireless network and the conference room of the conferencing gateway. 3.The method of claim 1, further comprising: in response to receiving therequest message for establishing the voice call, sending a requestmessage for establishing the first connection leg.
 4. The method ofclaim 1, further comprising: in response to receiving the requestmessage for establishing the voice call, sending to the mobile device acall redirection message which includes an address of the conferenceroom of the gateway.
 5. The method of claim 1, further comprising: inresponse to receiving the request message for establishing the voicecall, sending to the mobile device a Moved Temporarily message whichincludes an address of the conference room of the gateway, forredirecting the voice call so that the first connection leg may beestablished between the mobile device and the conference room of thegateway.
 6. The method of claim 1, wherein the request message forestablishing the second connection leg comprises a SIP INVITE message.7. The method of claim 1, wherein the request message for establishingthe second connection leg comprises a SIP INVITE message, the SIP INVITEmessage including an address of the gateway and call party informationcorresponding to the destination device.
 8. The method of claim 1,wherein the re-routing message for re-routing the second connection legcomprises a SIP REFER message.
 9. The method of claim 1, wherein there-routing message for re-routing the second connection leg comprises aSIP REFER message, the SIP REFER message including a REFER-TO headerwhich includes a source identifier corresponding to the conference roomof the gateway.
 10. The method of claim 1, wherein the networkprocessing component is co-located with the gateway.
 11. The method ofclaim 1, wherein the destination device is connected in a telephonenetwork.
 12. The method of claim 1, wherein the destination device isconnected in a public switched telephone network (PSTN) and thedestination device is a PSTN telephone device.
 13. A computer programproduct, comprising: a non-transitory computer readable medium; computerinstructions stored in the non-transitory computer readable medium; andthe computer instructions being executable by one or more processors ofa network processing component for performing a method for establishingvia a gateway a voice call between a mobile device which operates in awireless network and a destination device, wherein a first connectionleg of the voice call is to be established between the mobile device anda conference room of the gateway, the computer instructions beingfurther executable for: receiving from the mobile device a requestmessage for establishing the voice call which is directed to a selectedtelephone number of the destination device; in response to receiving therequest message for establishing the voice call: sending to the gatewaya request message for establishing a second connection leg between thenetwork processing component and the destination device; and sending tothe gateway a re-routing message for re-routing the second connectionlea from the network processing component to the conference room, forinitially establishing the voice call between the mobile device and thedestination device via the gateway, the voice call including the firstand the second connection legs.
 14. A network processing component foruse in establishing, via a gateway, a voice call between a mobile devicewhich operates in a wireless network and a destination device, wherein afirst connection leg of the voice call is to be established between themobile device and a conference room of the gateway, the networkprocessing component being configured to receive from the mobile devicea request message for establishing the voice call which is directed to aselected telephone number of the destination device; in response toreceiving the request message for establishing the voice call: send fromthe network processing component to the gateway a request message forestablishing a second connection leg between the network processingcomponent and the destination device; and send from the networkprocessing component to the gateway a re-routing message for re-routingthe second connection leg from the network processing component to theconference room, for initially establishing the voice call between themobile device and the destination device via the gateway, the voice callincluding the first and the second connection legs.
 15. The networkprocessing component of claim 14, which is further configured to send tothe mobile device a call redirection message which includes an addressof the conference room of the gateway in response to receiving therequest message for establishing the voice call.
 16. The networkprocessing component of claim 14, which is further configured to, inresponse to receiving the request message for establishing the voicecall, send to the mobile device a Moved Temporarily message whichincludes an address of the conference room of the gateway, forredirecting the voice call so that the first connection leg may beestablished between the mobile device and the conference room of thegateway.
 17. The network processing component of claim 14, wherein therequest message for establishing the second connection leg comprises aSIP INVITE message, the SIP INVITE message including an address of thegateway and call party information corresponding to the destinationdevice.
 18. The network processing component of claim 14, wherein there-routing message for re-routing the second connection leg comprises aSIP REFER message, the SIP REFER message including a REFER-TO headerwhich includes a source identifier corresponding to the conference roomof the gateway.
 19. The network processing component of claim 14, whichis co-located with the gateway.
 20. A method for use in a mobile devicefor initially establishing a voice call between the mobile deviceoperating in a wireless network and a destination device via aconferencing gateway which is configured to combine media streams ofconnection legs of the voice call, the method comprising: receiving, viaa user interface of the mobile device, a request for establishing thevoice call with the destination device, the request including a directinward dialing number of the destination device; in response toreceiving the request for establishing the voice call: sending, to theconferencing gateway, a message which includes the direct inward dialingnumber of the destination device; placing a call to a direct inwarddialing number of a telephone network interface of the conferencinggateway, the call being connected to the destination device identifiedby the direct inward dialing number from the message for initiallyestablishing the voice call between the mobile device and thedestination device.
 21. The method of claim 20, where the message sentto the gateway causes the conferencing gateway to match the message fromthe mobile device with the call from the mobile device for connectingthe call to the destination device identified by the direct inwarddialing number thereof.
 22. The method of claim 20, wherein the messagecomprises a short message service (SMS) message.